Putting a life logging app in the LINKLET

Putting a life logging app in the LINKLET

---

2025-03-05

https://gyazo.com/d5ef7d577255907bce3ff715364a13e9

once through

o3-mini-high.icon

This error is caused by missing credentials when retrieving the library from GitHub Packages. Please follow the steps below to address this issue.

Creating a GitHub Personal Access Token

Create a new token on GitHub under "Settings" -> "Developer settings" -> "Personal access tokens".

Be sure to grant "read:packages" permission when creating the file.

Add authentication information to local.properties ...

That's the one in the README.

https://gyazo.com/2bc6018940666acaa8c1c3ff63b381f9

o3-mini-high.icon

Please test on a compatible device.

Check if it is recognized by using the adb devices command.

% adb devices

List of devices attached

emulator-5554 device

Oh, just because it's connected and has a red light doesn't mean it's activated, I see.

Started up and went from light blue to green.

% adb devices

List of devices attached

P16M116D5252823 device

emulator-5554 device

OK

---

code::

2025-03-07 13:58:51: Launching app on 'QUALCOMM THINKLET LC01'.

Open logcat panel for QUALCOMM THINKLET LC01 (P16M116D5252823)

Connected to process 3550 on device 'qualcomm-thinklet_lc01-P16M116D5252823'.

It's done.

https://gyazo.com/12f76352976fb62153a2d6d22e321f64

Nothing was saved at all. I need to set the permissions.

$ adb shell am start -n ai.fd.thinklet.app.lifelog/.MainActivity --ez enabledMic true

$ adb shell ls /sdcard/DCIM/lifelog/19740103/

19740103_045124.raw

19740103_045125.gif

o3-mini-high.icon

There are two main transfer methods

How to use the adb command

Execute the following command in a terminal to copy files stored in the specified directory to your PC.

How to use MTP mode

Connect the device to USB and switch to "File Transfer (MTP)" mode from the notification area.

Access the device's internal storage with PC Explorer (for Windows) or Finder (for Mac) and copy the files in the DCIM/lifelog/ folder.

code::

% adb shell ls /sdcard/DCIM/lifelog/19740103/

19740103_045124.raw

19740103_045125.gif

% adb pull /sdcard/DCIM/lifelog/ ~/Downloads

/sdcard/DCIM/lifelog/: 2 files pulled, 0 skipped. 27.3 MB/s (78614272 bytes in 2.748s)

$ ffmpeg -f s16le -ar 48000 -ac 2 -i ~/Downloads/lifelog/19740103/19740103_045124.raw output.wav

I'll have to try actually walking and talking with it on.

2025-03-08

Test operation of [LINKLET

I thought maybe I shouldn't muffle it, but surprisingly it's not a problem.

https://gyazo.com/6357de17b18027861f8c2373fdea8fbb

code::

% adb shell ls /sdcard/DCIM/lifelog/19740104

19740104_005846.raw

% adb shell ls /sdcard/DCIM/lifelog/19740103

19740103_045124.raw

19740103_045125.gif

19740103_233158.raw

19740103_233159.gif

Hmm? Was this internally dated?

% adb pull /sdcard/DCIM/lifelog/ ~/Downloads

About 19 images were taken.

Maybe once every five minutes?

1. default setting: once every 300 seconds (5 minutes)

Definition at line 21 of file LifeLogArgs.kt

intervalSeconds = max(bundle?.get("intervalSeconds")?.toString()?.toIntOrNull() ?: 300, 10)

2. minimum interval: 10 seconds

Also in LifeLogArgs.kt, line 21, a minimum value of 10 seconds is set

Configuration by configuration file:

Which setting is actually used depends on how the app is launched. If the app is launched using a configuration file, the interval in that configuration file is applied. If the app is launched without a configuration, the default of 300 seconds (5 minutes) is applied.

---

As for the audio, I'll have to take a picture tomorrow.

2025-03-09

code::

% adb shell ls /sdcard/DCIM/lifelog/19740105/

19740105_033437.gif

19740105_033437.raw

19740105_050124.raw

19740105_062813.raw

19740105_075501.raw

19740105_092149.raw

19740105_104838.raw

That's a lot of audio files.

$ adb pull /sdcard/DCIM/lifelog/ ~/Downloads

$ ls -l ~/Downloads/lifelog/19740105

code::

total 10122120

-rw-r--r-- 1 nishio staff 11603521 3 9 23:52 19740105_033437.gif

-rw-r--r-- 1 nishio staff 1000000512 3 9 23:51 19740105_033437.raw

-rw-r--r-- 1 nishio staff 1000000512 3 9 23:53 19740105_050124.raw

-rw-r--r-- 1 nishio staff 1000000512 3 9 23:54 19740105_062813.raw

-rw-r--r-- 1 nishio staff 1000000512 3 9 23:52 19740105_075501.raw

-rw-r--r-- 1 nishio staff 1000000512 3 9 23:52 19740105_092149.raw

-rw-r--r-- 1 nishio staff 130837248 3 9 23:53 19740105_104838.raw

I see, so the audio file is split at 1GB.

Let's observe in Audacity

https://gyazo.com/0030b9dad8b2ead55b9b0c8743237664

https://gyazo.com/bfc03d2ee156b77269b098a1ade20ab6

1 GB for 1.5 hours

120MB for MP3

Throw to [NotebookLM

small proportion

https://gyazo.com/7afc773fe6d2de8af3911e2f920ab06e

There are difficulties in transcribing words like "Noda Crystal" and "plurality," but I think it's worthwhile to be able to look back and say, "Yes, that's what we talked about!" but it's worthwhile to be able to look back on what we talked about, since I often talk too much at once at these meetings and my memory overflows!

They should be able to dig into just the interesting stories and have them explained.

2025-03-10

https://gyazo.com/5c1db5e609309c0028fcfe7d571658c4

I'll think about it next time I do it.

code:bash

for f in ~/Downloads/lifelog/19740105/*.raw; do

ffmpeg -f s16le -ar 48000 -ac 2 -i "$f" "${f%.raw}.wav"

done

2025-03-15

https://pbs.twimg.com/media/GmAkIijbsAAjhKz?format=png&name=small#.png

https://pbs.twimg.com/media/GmAlIeLawAA_R46?format=png&name=medium#.png

@ukkaripon

@teramotodaiki

https://pbs.twimg.com/media/GmAlkf6aoAAK__o?format=png&name=medium#.png

---